翻訳と辞書
Words near each other
・ SystemImager
・ Systemin
・ Systeminfo.exe
・ Systemisch
・ Systemness
・ Systemography
・ Systempunkt
・ SystemRDL
・ SystemRescueCD
・ Systems analysis
・ Systems analysis and design
・ Systems analyst
・ Systems and Control
・ Systems and Synthetic Biology
・ Systems Applications Products audit
Systems architect
・ Systems architecture
・ Systems art
・ Systems biology
・ Systems Biology Graphical Notation
・ Systems Biology in Reproductive Medicine
・ Systems Biology Ireland
・ Systems Biology Ontology
・ Systems biomedicine
・ Systems Centered Therapy
・ Systems Commonwealth
・ Systems Concepts
・ Systems control
・ Systems design
・ Systems development life cycle


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Systems architect : ウィキペディア英語版
Systems architect


The systems architect is a professional figure in ICT. Systems architects define the architecture of a computerized system (i.e., a system composed of software and hardware) in order to fulfill certain requirements. Such definitions include: a breakdown of the system into components, the component interactions and interfaces (including with the environment, especially the user), and the technologies and resources to be used in the design.
The Systems Architect's work must avoid realization issues and readily permit unanticipated extensions/modifications in future stages. Because of the extensive experience required for this, the Systems Architect is typically a very senior technician with substantial, but general, knowledge of hardware, software, and similar systems. But above all, the systems architect must be reasonably familiar with the users' domain of experience (that is, the architect of an air traffic system needs to be more than superficially familiar with all of the tasks of an air traffic system, including those of all levels of users).
== Overview ==

Systems Architects interface with multiple stakeholders in an organization in order to understand the various levels of requirements, the domain, the viable technologies, and anticipated development. Their work includes determining multiple design alternatives, assessing such alternatives based on all identified constraints (such as cost, schedule, space, power, safety, usability, reliability, maintainability, availability, and so on), and selecting the most suitable options for further design. The output of such work sets the core properties of the system, and those that are hardest to change later.
In small systems the architecture is typically defined directly by developers. In larger systems, a Systems Architect may be appointed to outline the overall system and interface with the users and stakeholders. Very large, highly complex systems may include multiple architects, in which case the architects work together to integrate their subsystems or aspects, and may respond to a Chief Architect responsible for the entire system.
In systems design, the architects and engineers are responsible for:
* Interfacing with the user(s) and sponsor(s) and all other stakeholders in order to determine their (evolving) needs.
* Generating the highest level of system requirements, based on the user's needs and other constraints.
* Ensuring that this set of high level requirements is consistent, complete, correct, and operationally defined.
* Performing cost–benefit analyses to determine whether requirements are best met by manual, software, or hardware functions; making maximum use of commercial off-the-shelf or already developed components.
* Developing partitioning algorithms (and other processes) to allocate all present and foreseeable requirements into discrete partitions such that a minimum of communications is needed among partitions, and between the user and the system.
* Partitioning large systems into (successive layers of) subsystems and components each of which can be handled by a single engineer or team of engineers or subordinate architect.
* Interfacing with the design and implementation engineers and architects, so that any problems arising during design or implementation can be resolved in accordance with the fundamental design concepts, and user needs and constraints.
* Ensuring that a maximally robust design is developed.
* Generating a set of acceptance test requirements, together with the designers, test engineers, and the user, which determine that all of the high level requirements have been met, especially for the computer-human-interface.
* Generating products such as sketches, models, an early user guide, and prototypes to keep the user and the engineers constantly up to date and in agreement on the system to be provided as it is evolving.
* Ensuring that all architectural products and products with architectural input are maintained in the most current state and never allowed to become obsolete.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Systems architect」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.